home *** CD-ROM | disk | FTP | other *** search
- Path: EU.net!sun4nl!xs4all!usenet
- From: martijnl@xs4all.nl (Martijn Lievaart)
- Newsgroups: comp.lang.c++
- Subject: Re: Stack vs. Heap
- Date: 2 Jan 1996 15:03:38 GMT
- Organization: XS4ALL, networking for the masses
- Message-ID: <4cbhga$dra@news.xs4all.nl>
- References: <4bv41r$c4v@newsbf02.news.aol.com> <30e33866.9714880@nntp.ix.netcom.com> <30E40F67.27D5@ix.netcom.com>
- NNTP-Posting-Host: mas01-15.dial.xs4all.nl
- X-Newsreader: WinVN 0.99.6
-
- In article <30E40F67.27D5@ix.netcom.com>, susaned@ix.netcom.com says...
- .
- . (snip)
- .
- >
- >But make sure you're talking Global heap. The local heap is just as
- >limited as the stack (in fact you as the programmer decide how to allocate
- >your little 64k between stack and local heap). Plain old "new" is going to
- >allocate out of your local heap, like the Windows call LocalAlloc. You
- >have to use GlobalAlloc to get your storage from the big sandbox. All this
- >ridiculousness is enough to make us abandon 16-bit platforms and just write
- >for the 32's.
- >
- > - Ned Gladstone
-
- Oh come on, use the large model. Win16 is horrible enough but you don't have
- to put up with this. You're still limited (mostly) to 64K per object/array so
- it remains a pain in the ass. I also prefer a serious OS over (most) M$
- products but who said this was a perfect world?
-
-